https://github.com/ma-laforge/InspectDR.jl/blob/master/notebook/2_interact.ipynb

FWIW, the changes you made at ma-laforge/LibPSF.jl@7308f14 are not really correct, as they mean you won't accept non-standard string types. Just use Compat.jl without changing the code at all.

Other changes look OK.

Thanks for the comment. I might be wrong here (correct me if so), but from what I understood:

File paths (in Julia? / on modern computing systems in general?) are supposed to be stored/manipulated as UTF8 strings (Not UTF16, nor UTF32, nor...).

Now, from my understanding: since v0.5 of Julia, I should be using type String - because UTF8String is now deprecated and merged with ASCIIString.

I used to generate function signatures with ::AbstractString on file paths simply out of laziness. If I used the suggested UTF8String instead, someone making a function call using an ASCIIString would either have to explicitly upconvert to UTF8String - or I (as the module developer) would have to make duplicate function signatures to support ASCIIString file paths (thus the laziness).

As for using String for signal names: I am not convinced the PSF file format even supports UTF8 strings at all. I was debating throwing an exception if !(isascii(signame))... but opted to maintain support for UTF8 strings... just in case it worked.

Bump. I think that the discussion is ancillary, and that this can be merged--is this correct?

@kmsquire: If the question was directed at me, than yes: This PR is ready/waiting for a merge.